-
Notifications
You must be signed in to change notification settings - Fork 944
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating upgrade guide #5001
Updating upgrade guide #5001
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
## What are you changing in this pull request and why? <!--- Describe your changes and why you're making them. If related to an open issue or a pull request on dbt Core, then link to them here! To learn more about the writing conventions used in the dbt Labs docs, see the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md). --> Part 1 of #4998 ## Checklist <!-- Uncomment when publishing docs for a prerelease version of dbt: - [ ] Add versioning components, as described in [Versioning Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages) - [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade) --> - [ ] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. - [ ] For [docs versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning), review how to [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content). - [ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch." Adding or removing pages (delete if not applicable): - [ ] Add/remove page in `website/sidebars.js` - [ ] Provide a unique filename for new pages - [ ] Add an entry for deleted pages in `website/vercel.json` - [ ] Run link testing locally with `npm run build` to update the links that point to deleted pages
Merging unit tests
Adding indirect selection
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
|
||
Before v1.8, when you installed an adapter, you would automatically get `dbt-core ` installed along with the adapter package (if you didn’t already have an existing, compatible version of dbt-core). | ||
|
||
Beginning in v1.8, you must install _both_ dbt-core and the desired adapter. A new `pip` installation needs to look like this: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@matthewshaver In the issue, Grace suggested adding a link tot he migration guide:
link to the migration guide for adapter maintainers: dbt-labs/dbt-adapters#87
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great and some awesome info there! some small suggestions and link fix!
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
….8.md Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
….8.md Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
….8.md Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
….8.md Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
….8.md Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, love the linking to the github discussion for the adapters change!
Closes #4998
What are you changing in this pull request and why?
Updating the 1.8 migration guide with:
Checklist
Adding or removing pages (delete if not applicable):
website/sidebars.js
website/vercel.json
npm run build
to update the links that point to deleted pages